Skip to content

BUG: TypeError when doing equality comparison with Extension Dtype #44618

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 147 commits into from
Closed

BUG: TypeError when doing equality comparison with Extension Dtype #44618

wants to merge 147 commits into from

Conversation

ata-turhan
Copy link
Contributor

@ata-turhan ata-turhan commented Nov 25, 2021

ata-turhan and others added 17 commits November 25, 2021 18:58
…rser (#44599)

* BUG: Providing fix for GH#44366

* BUG: fix pre-commit run

* BUG: adding other API changes for change of default argument

* Rewriting if statement and adding test

* BUG: changing pd.Series to Series to validate pre-commit hook

* Removing the second whatsnew statement only to keep the bug fix one

* BUG: simplifying the test with parser and parse_dates False #44366

* BUG: fixing pre-commit #44366
@ata-turhan ata-turhan closed this Nov 25, 2021
@ata-turhan ata-turhan reopened this Nov 25, 2021
@pep8speaks
Copy link

pep8speaks commented Nov 25, 2021

Hello @fotino21! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

Line 400:89: E501 line too long (100 > 88 characters)

Comment last updated at 2021-12-05 10:54:23 UTC

@jreback jreback changed the title test added for issue #43038 BUG: conpare int64 and Int64 Nov 25, 2021
@@ -391,6 +392,41 @@ def test_is_unsigned_integer_dtype(dtype):
def test_is_not_unsigned_integer_dtype(dtype):
assert not com.is_unsigned_integer_dtype(dtype)

def test_all_type_comparison():
assert pd.api.types.pandas_dtype("int_") == "int_"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pls paramterize instead of writing out like this

Copy link
Contributor Author

@ata-turhan ata-turhan Nov 28, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made the change you requested @jreback

@jreback jreback changed the title BUG: conpare int64 and Int64 BUG: compare int64 and Int64 Nov 26, 2021
@jreback
Copy link
Contributor

jreback commented Dec 6, 2021

something when wrong

@ata-turhan
Copy link
Contributor Author

@jreback I didn't understand

@ata-turhan ata-turhan requested a review from jreback December 6, 2021 16:38
@jreback
Copy link
Contributor

jreback commented Dec 6, 2021

@fotino21 you are updating a huge amount of code. make sure you are merging in master

@ata-turhan
Copy link
Contributor Author

@fotino21 you are updating a huge amount of code. make sure you are merging in master

@jreback My changes are small and they are only in test_common file. What do i need to do for other commits by other people. And sorry for the inconvenience. This is my first contribution to a huge code base.

@ata-turhan
Copy link
Contributor Author

@jreback @phofl Do I need to do anything else before merge?

@jreback
Copy link
Contributor

jreback commented Dec 7, 2021

@jreback @phofl Do I need to do anything else before merge?

yes you need to rebase against upstream master

@ata-turhan
Copy link
Contributor Author

@jreback @phofl Do I need to do anything else before merge?

yes you need to rebase against upstream master

@jreback I made it following this link: https://timonweb.com/misc/how-to-update-a-forked-repo-from-an-upstream-with-git-rebase-or-merge/

@ata-turhan ata-turhan requested a review from phofl December 8, 2021 12:24
@ata-turhan
Copy link
Contributor Author

@jreback @phofl Do I need to do anything else before merge?

@jreback
Copy link
Contributor

jreback commented Dec 9, 2021

@fotino21 this has included lots of other changes u need to merge upstream/master

@ata-turhan
Copy link
Contributor Author

@fotino21 this has included lots of other changes u need to merge upstream/master

@fotino21 this has included lots of other changes u need to merge upstream/master

How can i do that? I already based my master branch to upstream/master

@MarcoGorelli
Copy link
Member

MarcoGorelli commented Dec 10, 2021

can you try

git fetch upstream
git rebase -i upstream/master
git push origin HEAD -f

?
In the second step, you should get an interactive window, and you can choose which commits to keep / edit

@ata-turhan
Copy link
Contributor Author

@MarcoGorelli

In the second step, I only see this message:

noop

Rebase bc17343..bc17343 onto bc17343 (1 command)

Commands:

p, pick = use commit

r, reword = use commit, but edit the commit message

e, edit = use commit, but stop for amending

s, squash = use commit, but meld into previous commit

f, fixup [-C | -c] = like "squash" but keep only the previous

commit's log message, unless -C is used, in which case

keep only this commit's message; -c is same as -C but

opens the editor

x, exec = run command (the rest of the line) using shell

b, break = stop here (continue rebase later with 'git rebase --continue')

d, drop = remove commit

l, label = label current HEAD with a name

t, reset = reset HEAD to a label

m, merge [-C | -c ] [# ]

. create a merge commit using the original merge commit's

. message (or the oneline, if no original merge commit was

. specified); use -c to reword the commit message

These lines can be re-ordered; they are executed from top to bottom.

If you remove a line here THAT COMMIT WILL BE LOST.

However, if you remove everything, the rebase will be aborted.

@MarcoGorelli
Copy link
Member

🤔 to be honest I don't know, I can't even tell how you opened this PR as it doesn't appear to have come from a branch

the other PR (#44840) does come from a branch, so maybe it's OK to continue there, then I can check it out locally if necessary

@jreback
Copy link
Contributor

jreback commented Dec 10, 2021

closing in favor of #44840

@fotino21 ideallly we only have a single, original PR as it makes more work for maintaining.

@jreback jreback closed this Dec 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dtype Conversions Unexpected or buggy dtype conversions ExtensionArray Extending pandas with custom dtypes or arrays.
Projects
None yet
Development

Successfully merging this pull request may close these issues.